Add missing upgrade doc - #31226
Merged
Merged
Conversation
jonathanfrappier
added
pr/no-milestone
hashicorp-contributed-pr
|
CI Results: |
|
Build Results: |
brianshumate
previously approved these changes
Jul 8, 2025
yhyakuna
previously approved these changes
Jul 8, 2025
jonathanfrappier
dismissed stale reviews from yhyakuna and brianshumate
via
July 8, 2025 18:06
86755af
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a missing upgrade document for HA deployments and fixes a broken link in the replication guide
- Added a new “vault-ha-upgrade” page under the upgrade directory
- Updated the site navigation to include the HA upgrade page
- Fixed the link in
replicated-deployment.mdxto point to the new upgrade path
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| website/data/docs-nav-data.json | Added nav entry for “Manual upgrade for HA deployments” |
| website/content/docs/upgrade/vault-ha-upgrade.mdx | New HA upgrade guide for pre-1.11 and opt-out scenarios |
| website/content/docs/upgrade/replicated-deployment.mdx | Updated link to the HA upgrade guide under /upgrade |
Comments suppressed due to low confidence (2)
website/data/docs-nav-data.json:982
- [nitpick] The nav title (‘Manual upgrade for HA deployments’) doesn’t match the page title (‘Vault HA upgrades without Autopilot Upgrade Automation’). Consider aligning the nav entry title with the document’s H1/frontmatter title for consistency.
"title": "Manual upgrade for HA deployments",
website/content/docs/upgrade/vault-ha-upgrade.mdx:13
- The link anchor
#automated-upgradediffers from the later link using#automated-upgrades. Verify the correct anchor in the target page to avoid a broken link.
- Opt-out the [Autopilot automated upgrade](/vault/docs/concepts/integrated-storage/autopilot#automated-upgrade) features with Vault 1.11 or later
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
yhyakuna
previously approved these changes
Jul 8, 2025
yhyakuna
approved these changes
Jul 8, 2025
9 tasks
Erfankam
pushed a commit
to Erfankam/vault
that referenced
this pull request
Sep 1, 2025
* Add missing upgrade doc * Add doc nav * Update website/content/docs/upgrade/vault-ha-upgrade.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update website/content/docs/upgrade/replicated-deployment.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Remove duplicate redirect --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
What does this PR do?
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.
PCI review checklist
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.